-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
chore(react-query): update peer-deps for react19 in v4 #9310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: v4
Are you sure you want to change the base?
Conversation
View your CI Pipeline Execution ↗ for commit 5310479
☁️ Nx Cloud last updated this comment at |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 5310479:
|
I can't reproduce the issue in the local test environment. Is there a problem with the CI pipeline? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’m in favor of adding React 19 to the peerDependencies of @tanstack/react-query v4.
Since it seems that @TkDodo previously opposed this change, I wanted to tag you and check if you’re okay with it before merging.
From what I understand, there’s nothing in @tanstack/react-query v4 that should cause issues with React 19.
If there are any problems, I’d expect them to be due to changes in React itself — so I think it should be safe to go ahead with the merge. Would that be alright with you?
we can bump the peerDependency if everything works at runtime, but I don’t think we’re running tests against react19. |
related: #8441
I'm the maintainer of Suspensive (a community project for React Query), who previously submitted a PR regarding React 19 support in React Query v4.
This time, I'd like to explicitly specify React 19 in the
peerDependencies
instead of thedependencies
. React Query v4 is already compatible with React 19 without any code changes, and we've confirmed this through the following steps:pnpm pack
) with React 19 specified inpeerDependencies
There are no breaking changes in React 19 that affect compatibility, and v4 works reliably without special handling. If issues do arise, they would likely be due to changes in React 19, not React Query v4 itself.
Currently, since React 19 is not listed in
peerDependencies
, usingreact-query@v4
in a React 19 environment causes the following problems: